seeing those: ```20:41:15.86 [WARN] DEPRECATED: No...
# development
p
seeing those:
Copy code
20:41:15.86 [WARN] DEPRECATED: Not setting `Goal.environment_migrated=True` for `Goal` `auth-token-info` is scheduled to be removed in version 2.17.0.dev0.

See <https://www.pantsbuild.org/v2.15/docs/plugin-upgrade-guide>

20:41:15.86 [WARN] DEPRECATED: Not setting `Goal.environment_migrated=True` for `Goal` `auth-token-check` is scheduled to be removed in version 2.17.0.dev0.

See <https://www.pantsbuild.org/v2.15/docs/plugin-upgrade-guide>
Screen Shot 2022-10-13 at 4.43.19 PM.png
can someone point me in the right direction so I can address those deprecations ?
w
sorry: this is https://github.com/pantsbuild/pants/issues/17129@ancient-vegetable-10556 is currently working on those, and we hope to have all of them resolved before cutting
2.15.x
. if we don’t have all of them resolved by then (or don’t want that time pressure), we could do something to silence the deprecation only for the built-in/core goals, while still triggering it for plugins
as to addressing the deprecation in plugins: here is the page that will be at that URL as soon as the 2.15.x docsite is published: https://github.com/pantsbuild/pants/blob/main/docs/markdown/Writing%20Plugins/common-plugin-tasks/plugin-upgrade-guide.md#environment[…]ariables-etc
a
Actually, those look like goals added by the toolchain plugin. I suspect they can just be resolved by marking the migration as done and moving on?
f
yeah the toolchain goals don't do builds so they should have no need to compute an
EnvironmentName
w
depends whether they 1) invoke a process, 2) look at environment variables… but possibly.
a
Or do we want to make them explicitly request the local environment?
b
As a stopgap, anyone wanna add to
ignore_warnings
? 🙂
a
@witty-crayon-22786 Only pants config environment variables
w
yea: try it and see if toggling the
Goal.environment_migrated
flag succeeds
I don’t think you should need to do anything more.
w
As a stopgap, anyone wanna add to
ignore_warnings
?
i’d feel better about skipping ahead to do:
we could do something to silence the deprecation only for the built-in/core goals, while still triggering it for plugins
…otherwise we might miss some and forget that we’re still showing the warning to users
b
okie doke
p
just want to get ahead of this. thank you all for the help, will get a version of the plugin that addresses those deprecations in the next week or so. FWIW, the toolchain plugin does use env variables (read the values of some of them) to help with CI integration (it basically reads some env variables set by the CI system)
w
FWIW, the toolchain plugin does use env variables (read the values of some of them) to help with CI integration (it basically reads some env variables set by the CI system)
yea… you’ll probably want to use
ChosenLocalEnvironmentName
for that, as mentioned in the doc
p
also in CI, the auth token value is read from an env variable. see: https://docs.toolchain.com/docs#configure-pants-to-use-remote-caching-in-your-ci-environment
a
OK, I can help you out with the environment variables side of things when the time comes, just ping me or Stu
w
@polite-garden-50641: or… hm. actually, that’s the AuthPlugin/StreamingWorkunitsPlugin … those may just continue to get an environment automatically for now?
this deprecation is primarily about Goals
p
w
thanks!