feat(cmd): Add windsor build-id command #1536
Merged
+1,493
−8
Conversation
This file contains hidden or 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
The `windsor build-id` command is used to manage an incremental build ID for local development purposes. This build ID always increments as it is generated from the unix epoch time stamp. The `windsor build-id --new` flag triggers the creation of a new build ID.
The build ID is stored in a `.windsor/.build-id` file. It is exported as the `BUILD_ID` env var, as well as made available throughout the cluster configuration using the ${BUILD_ID} post build variable.
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.
A build ID can be generated by running
windsor build-id --new. This mechanism creates aBUILD_IDenvironment variable, and injects aBUILD_IDas a post build in the kubernetes cluster.Bulid IDs are formatted
YYMMDD.RND.#Which includes a date, random ID, and an incrementing integer. This mechanism can be used for tagging and deploying images to the local development cluster. Each
windsor installwill trigger an update to the build ID if it has changed, triggering a redeploy.