Radek Simko 78a333060e command/init: Only install PSS provider early (#38648) ... This walks back some of the decisions we made earlier around two-step provider downloading process. However, it should not impact the safety features and it should not have a tangible (functional) impact on the end-user aside from the log output outlined below. The motivation is to accommodate some needs of the upcoming policy features. Previously the two steps were: 1. Download providers based on configuration 2. Download providers based on state The process remains two steps but the new steps are: 1. Download 0-1 provider if one is needed for PSS (PSS is in use) 2. Download all other providers (configuration + state) End-user facing changes are mainly related to terminal output - what messages are included and their order: - initializing_provider_plugin_message (re-introduction after removal in 1.14) - initializing_state_store_provider_plugin_message (net new but PSS specific)		2026-06-05 17:37:32 +01:00
..
config-and-state-different-providers	PSS: Add alternative, experimental version of init command that downloads providers in two stages (#37350)	2025-08-18 11:20:18 +01:00
config-and-state-same-providers	PSS: Add alternative, experimental version of init command that downloads providers in two stages (#37350)	2025-08-18 11:20:18 +01:00
config-state-file-and-lockfile	PSS: Add alternative, experimental version of init command that downloads providers in two stages (#37350)	2025-08-18 11:20:18 +01:00
state-file-only	PSS: Add alternative, experimental version of init command that downloads providers in two stages (#37350)	2025-08-18 11:20:18 +01:00
state-store-config-only	command/init: Only install PSS provider early (#38648)	2026-06-05 17:37:32 +01:00