planBuildFileResource doesn't support optional file resources

[nrobinaubertin]

bind-operator is declaring a file resource in its metadata but it is entirely optional and mostly there for debugging purposes.

Since #454, I can't pass integration tests anymore because operator-workflow is asking me to provide a script to build this resource. That doesn't really make sense in my case, the snap file is handled in a different repository.

Is there a way to opt out of this behavior ?

[javierdelapuente]

@weiiwang01 can you have a look at this issue? Thanks!

[weiiwang01]

Is this debugging file resource used often? If not, maybe remove this resource definition from charmcraft.yaml and adding it back locally when needed? This has the additional benefit of ensuring the charmhub version will not have the resource defined.

[nrobinaubertin]

I use it often locally and could imagine use-cases where this comes handy in production if we need to hotfix the snap for example.
Is it an issue if the charmhub version has an optional resource defined ?

[weiiwang01]

I am not entirely sure if a resource can be defined but not uploaded on Charmhub. It definitely can be now, but I am not sure if this is by design.

How about adding a marker to the resources? For example, we could prefix the description with (local) and skip the resource in the workflows. What do you think?

[nrobinaubertin]

Yes, that's a good workaround idea (it would work for me at least). So instead of description: charmed-bind snap file for debugging purposes, I would write description: (local) charmed-bind snap file for debugging purposes ?

[weiiwang01]

Pull request created: #493