Consistent Kubernetes service object naming #399
Merged
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.
Resolves spring-cloud/spring-cloud-skipper#953
While an issue that is due to Skipper's versioning, there was more flexibility to handle these cases in deployer...
Depends on Skipper built with spring-cloud/spring-cloud-skipper#977 so we can get the actual non-versioned app name..
Below are the test case steps I have tested this with. Seems to cover the basis that's been discussed. AT's other other testing may reveal other issues...
* app register --name log --type sink --uri docker://springcloudstream/log-sink-rabbit:2.1.4.RELEASE
* stream update --name ticktock55 --properties version.log=2.1.4.RELEASE