rhythmic-finland-3625601/27/2020, 3:05 PM
which is a nice way of abstracting a certain part of the whole into a separate file. This makes the projects more readable as we now can find resources easier than in a long list of resources inside a single index.ts file. As we also started using pulumi for more than just one project, I’d like to be able to reuse those components in other projects without copy/pasting single classes between them (which is already way better than to copy/paste many lines of resources from an index.ts).
• Is there some best practice project structure for such
• How do you deal with testing the resources if there is no pulumi project? Having a separate repo for the pulumi project that uses the library via npm link?
• How to handle dependencies on pulumi resources? I assume the library should not bring specific versions of pulumi providers with it? Is using
the way to go?
limited-rainbow-5165001/27/2020, 3:41 PM
rhythmic-finland-3625601/27/2020, 3:45 PM
best-summer-3825202/11/2020, 9:27 AM
rhythmic-finland-3625602/24/2020, 12:42 PM
- should this exact version be given to the user of my module, too? Maybe the user started yesterday and already uses
which has some bugfixes. Not sure how this behaves then.
limited-rainbow-5165002/24/2020, 12:51 PM
but do not publish a lock file to the registry. The given version specifier uses 1.4.3 as the minimum version but will use a later 1.4.x version when available
rhythmic-finland-3625602/24/2020, 12:56 PM
. When someone else installs my library, they will have their own lock-file tracking also transitive dependencies, right?
but might choose the version on their own?
limited-rainbow-5165002/24/2020, 1:13 PM
rhythmic-finland-3625602/24/2020, 1:39 PM
boundless-airport-9905202/25/2020, 8:17 AM
How to deal with testingI have a nested pulumi project that imports the component in parent folder
And before releasing the component, I do unit tests on the component itself and do a
import * as lib from '../index'
on the pulumi project. I think I can go further by doing a real
during testing phase.
How to handle dependenciesFor the moment, I only add
and let main project configure dependencies version. But I’m not sure it’s the best way to deal with dependencies, especially if you publish your component publicly