feature :: update status for developer inactive/active #223
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
|
@vivianvarela - As per this link, the status is an output field only, so I would not want to include it in the payload. If someone tries to create a developer with "status", it could fail. Set Developer Status is a separate operation. If you inactivate the developer by mistake while trying to update other fields of the developer, it could automatically disable all keys within the developer apps. Better we dont include this as part of update but create a new Maven goal |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Type of Change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Code quality/refactoring
This pull request introduces a new capability to the apigee-config-maven-plugin to manage a developer's status (active/inactive). This functionality was implemented to support CI/CD pipelines where developer status needs to be updated automatically based on configuration files checked into source control.