docs: moving a pipeline from the run-experiment action - #83
Merged
Merged
Conversation
…g deprecated The action is not rebuilt on the CLI after all: customers move to the CLI. The README maps each of the action's inputs to a flag and its outputs to the JSON report, and the changelog and the platform test no longer speak of the action running on the CLI.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Instead of rebuilding
steadybit/run-experimenton top of the CLI, the action will be deprecated slowly, and customers move to the CLI. None of the wrapper was written, so nothing is removed; this only changes what the repository says.experiment runflag or variable, including the units that differ (ms in the action, a duration here). It also shows how to get the action's outputs from--report run.json. One difference is spelled out: the action retries 3 times while another experiment runs by default, and the CLI only does so with--busy-retries.The parity flags from v6.2.0 stay. They are what makes the move a flag-for-flag change.
Deprecating the action itself happens in
steadybit/run-experiment, and is not part of this PR: a deprecation notice in its README, and adeprecationMessageon the action or a warning in its log pointing here.