Whenever I do an export of an object created from a custom made pulumi.ComponentResource, preview will always show changes on that output. Has anyone run into this and found a way around it? I'm attempting to have the ComponentResource class attributes be outputs but I don't want it to always show diffs

That's not something Are the exported properties Outputs? Or just primitives?

Mix of pulumi.output<strings> and strings

Nothing is occurring. Can you create a snippet example?

~ firebaseComponent    : {
        firebaseDatabaseName: "removed"
        firebaseDatabaseUrl : "removed"
        urn                 : "removed"
    }

Output diff looks something like this

Can you show how those properties are set, and how the exports are done? You can use the Text Snippet feature in the + menu

export (cut off the inputs):

export const firebaseComponent = new FirebaseComponent('firebase', {

class definition

export class FirebaseComponent extends pulumi.ComponentResource {
    public readonly firebaseDatabaseUrl: pulumi.Output<string>;
    public readonly firebaseDatabaseName: pulumi.Output<string>;

    constructor(name: string, props: FirebaseInterface, opts?: pulumi.ComponentResourceOptions) {

....

        const firebaseDatabase = new GoogleFirebaseInstanceResource(firebaseDatabaseName, {
            gcpProjectNumber: props.projectNumber,
            location: props.firebaseRegion,
            databaseId: firebaseDatabaseName,
        }, {
            parent: this,
            dependsOn: [firebaseProject],
        });

        this.firebaseDatabaseName = firebaseDatabase.id;

Ah. You're exporting an object, not a primitive / output. That's the expected result.

so I'd need to make a new object of the attributes of the class instead of just exporting the class object?

No. Exporting a class does nothing from Pulumi's point of view. Only data (objects / primitives / outputs) are relevant.

we've got downstream stacks already depending on the attributes (

firebaseComponent.firebaseDatabaseName

for example) so in order to not break functionality I'd have to still make an object, but understood

You can create the object on the other side. You can export the values individually.

Yeah was just hoping to find something like an ignoreChanges I could use to ignore whatever hidden attribute is changing, but I'll just make new ones to export so we don't have to change downstream too

You could try ignoreChanges. It's an opt.

makes sense