cs: allow environment-controlled volatility of objects#8
Open
okt-konst wants to merge 2 commits into
Open
Conversation
Allow object volatility to be controlled by environment variables. This allows users to make particular objects volatile depending on the host configuration. Signed-off-by: Viacheslav Galaktionov <viacheslav.galaktionov@oktet.tech>
This may be required on some networks where routes are periodically updated. One such example is AWS, where routes may occasionally change their metric value. Signed-off-by: Viacheslav Galaktionov <viacheslav.galaktionov@oktet.tech>
Collaborator
Author
|
@ol-arteman @arybchik could you please review? |
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
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.
Allow object volatility to be controlled by environment variables, so
particular objects can be made volatile depending on host configuration,
and use it to make agent routes optionally volatile. The latter is needed
on networks where routes are periodically updated behind TE's back - e.g.
on AWS, where routes may occasionally change their metric.
Commits: