feat!: Move location of terraform provider endpoint #51
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 is being done to segregate mirror endpoints from other endpoints such as API endpoints. We are doing this early in the project to prevent issues with namespacing in the future (i.e. imagine a hostname being hosted at `api` on an internal network). To allow users to migrate from the old location, we will make one release to simultaneously support the endpoints at the old location which could be deployed as a stepping stone release so no downtime is incurred from a version upgrade.
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.
This is being done to segregate mirror endpoints from other endpoints such as API endpoints.
We are doing this early in the project to prevent issues with namespacing in the future (i.e. imagine a hostname being hosted at
apion an internal network).To allow users to migrate from the old location, we will make one release to simultaneously support the endpoints at the old location which could be deployed as a stepping stone release so no downtime is incurred from a version upgrade.