Add flow property updates ADR and specification extensions #91
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.
Details
This PR came about because an question was raised about whether the Flow
source_id
can be updated. The proposal is to allow it to be updated to fix incorrect values for example. This may be restricted by systems that sit in front of TAMS API that check permissions for example.This PR offers some changes wrt updating Flow properties but proposes no change at this stage. Requirements may arise in future that changes this.
This PR adds endpoints for bit rate (see also #86) and flow collection properties. This is to make it consistent with other properties that are likely to be updated.
Pivotal Story (if relevant)
Story URL: https://www.pivotaltracker.com/story/show/188210268
Related PRs
Where appropriate. Indicate order to be merged.
Submitter PR Checks
(tick as appropriate)
Reviewer PR Checks
(tick as appropriate)
Info on PRs
The checks above are guidelines. They don't all have to be ticked, but they should all have been considered.