Optionalopts: ComponentResourceOptionsReadonlypathWhere this app's configuration lives, trailing slash included.
ReadonlyprojectThe project slug (the component name), e.g. cfx-deposit-api.
ReadonlyurnThe stable logical URN used to distinctly address a resource, both before and after deployments.
Every key this app holds, read once per program and merged with this
program's puts. The first call seals the puts: a later putSecret throws.
ProtectedgetRetrieves the data produces by initialize. The data is
immediately available in a derived class's constructor after the
super(...) call to ComponentResource.
Returns the provider for the given module member, if one exists.
ProtectedinitializeCan be overridden by a subclass to asynchronously initialize data for this component automatically when constructed. The data will be available immediately for subclass constructors to use. To access the data use getData.
Optionalopts: ComponentResourceOptionsOptionalname: stringOptionaltype: stringWrite a value this program computed, as a SecureString this stack owns.
visibility: "unmasked" stores a plain String for a non-secret value.
Optionalopts: { visibility?: string }ProtectedregisterRegisters synthetic outputs that a component has initialized, usually by allocating other child sub-resources and propagating their resulting property values.
Component resources can call this at the end of their constructor to indicate that they are done creating child resources. This is not strictly necessary as this will automatically be called after the initialize method completes.
Optionaloutputs: Inputs | Promise<Inputs> | Output<Inputs>StaticisReturns true if the given object is a CustomResource. This is designed to work even when multiple copies of the Pulumi SDK have been loaded into the same process.
A package's configuration in SSM Parameter Store: one SecureString per key under appSecretsPath, in this stack's account. Reads what a person set, and owns the parameters this program computes (
putSecret).The stack IS the environment: the dev stack runs in the dev account and reads the dev parameters, prod in prod. The path is the same in both.