Re: upgrading from atmos 1.168.0 to latest version...
# atmos
r
Re: upgrading from atmos 1.168.0 to latest version, the
ignore_missing_template_values
(link) seems to be the method @Pablo Paez found. Is there anyway to set this at a more global level than on every imported catalog ? e.g.
Copy code
import:
  - path: "<path_to_atmos_manifest2>"
    context: {}
    skip_templates_processing: false
    ignore_missing_template_values: true
e
I think it would be fair to introduce a feature Flagg for this
Can you open the GitHub issue and post it here?
๐Ÿ‘€ 1
Answer your question directly: no, I donโ€™t think itโ€™s possible
๐Ÿ‘ 1
r
Do you think this kind of setting would be acceptable ?
Copy code
settings:
  ignore_missing_template_values: true
e
It would be something under
settings.templates
, I believe.
r
Thanks Erik. What do you think about this https://github.com/cloudposse/atmos/pull/2158 ?
a
thanks RB, we'll implement it it will be under templates.settings
๐Ÿ™Œ 1
e
Oops, you're right @RB
templates.settings
(not
settings.templates
); this is before we properly standardized that top-level config values correspond to top-level atmos commands.
๐Ÿ‘ 2
r
no worries, i figured it was a typo
thanks for considering the change
when will this be available in the next release? i noticed that there are quite a few โ€œtestโ€ releases for 1.208.1.x
e
Yeah, those are related to the atmos native CI.
We cut those releases so it's easy to test binaries built from feature branches.
We hope to merge the native CI stuff this week for the first pass.
๐Ÿ™Œ 1
We do have quite a lot of PRs in the backlog subject to manual verification.
if you test your pr with
atmos .... --use-version 2158
you can tell us if it works or not
That requires CI to pass.
Well, that requires the build part of CI to pass.
r
Nice, yes, this works as expected ๐Ÿ™‚
@Erik Osterman (Cloud Posse) @Andriy Knysh (Cloud Posse) weโ€™re good to merge on 2158 if you folks are
๐Ÿ‘ 1
a
will merge today, it will be in the next release next week
๐Ÿ™Œ 1