You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In short, pulumi/pulumi#17810 introduced the protobuf changes required for the provider-side implementation. With those, a provider can:
Declare that it supports autonaming configurations with a response flag in Configure
Accept two extra properties in CheckRequest: a proposed name and a mode to apply it
We need to implement autonaming configuration for all bridged providers. The bridge should pass the configuration from CheckRequest all the way down to the autonaming module. The module itself will be able to understand the modes and use the proposed name appropriately. Once a bridged provider upgrades its bridge version, autonaming configuration should highlight in it autonamically.
The text was updated successfully, but these errors were encountered:
Hello!
Issue details
Implement the bridge part of pulumi/pulumi#1518. See pulumi/pulumi#17592 for the full design.
In short, pulumi/pulumi#17810 introduced the protobuf changes required for the provider-side implementation. With those, a provider can:
We need to implement autonaming configuration for all bridged providers. The bridge should pass the configuration from CheckRequest all the way down to the autonaming module. The module itself will be able to understand the modes and use the proposed name appropriately. Once a bridged provider upgrades its bridge version, autonaming configuration should highlight in it autonamically.
The text was updated successfully, but these errors were encountered: