Add tags to the provisioned EC deployment #3114
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds some tags to the provisioned elastic cloud deployment so that we can trace easily which deployment was created from which BK build job. Signed-off-by: Alexandros, Sapranidis <[email protected]>
Signed-off-by: Alexandros, Sapranidis <[email protected]>
nchaulet
approved these changes
Nov 20, 2023
|
SonarQube Quality Gate
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the problem this PR solves?
This commit adds some tags to the provisioned elastic cloud deployment so that we can trace easily which deployment was created from which BK build job.
How does this PR solve the problem?
// Explain HOW you solved the problem in your code. It is possible that during PR reviews this changes and then this section should be updated.
Because of an internal process, we would like to know easily which PR creates what resources in Elastic Cloud. This PR adds some tags to the autogenerated deployment for easier traceability
This has no impact on the existing fleet-server code base.