This was flagged by a conversation about some trailing 'activation' text in another context.
Upon review, we still have some vestiges of activation support.
Because globus endpoint is-activated, in particular, may be in use in long-standing scripts, these commands are given some extra deference.
They are already marked deprecated and hidden from help text and docs, but now they have their original functions replaced with an echo to stderr with a warning about upcoming removal.
This is even gentler than a removal (or, equivalently, a usage error), and precedes a likely upcoming release in which these commands will be outright removed.
activate, deactivate, and is-activated now all warn to stderr when used, and no longer have any other effects -- tests are updated to check this
--skip-activation-check for task submission commands is now hidden -- and commented as a deprecated option but not otherwise changed
remove activation helper functions
remove the autoactivate success fixture data from tests
remove Activated from globus endpoint show text output
This was flagged by a conversation about some trailing 'activation' text in another context. Upon review, we still have some vestiges of activation support.
Because
globus endpoint is-activated, in particular, may be in use in long-standing scripts, these commands are given some extra deference. They are already marked deprecated and hidden from help text and docs, but now they have their original functions replaced with an echo to stderr with a warning about upcoming removal. This is even gentler than a removal (or, equivalently, a usage error), and precedes a likely upcoming release in which these commands will be outright removed.activate,deactivate, andis-activatednow all warn to stderr when used, and no longer have any other effects -- tests are updated to check this--skip-activation-checkfor task submission commands is now hidden -- and commented as a deprecated option but not otherwise changedActivatedfromglobus endpoint showtext output