4.0.1 Export to directory fails on exporting hooks
See original GitHub issueDescription
When runnings an export to a directory structure, the export fails on exporting hooks
Reproduction
Running command a0deploy export -c config.json -f directory -o . fails with:
2020-02-10T22:10:25.910Z - error: Problem running command export
2020-02-10T22:10:25.910Z - error: Problem exporting hooks
Environment
- a0deploy 4.0.1
- macOS Mojave and macOS Catalina
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (2 by maintainers)
Top Results From Across the Web
customHooks module.exports not importing with es6 style
Let me know what you think the issue is. I have tried to change it from import to require() and it resolves the...
Read more >Exporting all Vector Directory Numbers - Avaya Documentation
In the navigation pane, click Call Center > Vector Directory Number . Select one or more Communication Manager instance from the Communication Manager...
Read more >Commit hooks are skipped due to PATH issues - Jira - Atlassian
This is still an issue, and a big one. We get many commits that fail in CI that should have failed in pre-commit...
Read more >How to integrate React Hooks into your project without ...
So create a hooks_container.js file in the hooks directory and set ... to do is change the export statements instead of exporting default....
Read more >Release Notes Knopflerfish 4.0.0 (OSGi R4 v4.3)
A set of hooks have been added with allows bundles to plug-into the ... Added export command that exports all matching configurations as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@dominicfallows I ran into a similar issue. I think this might be a problem for hooks created a while ago. The name property was missing on my hooks, possibly because there was no option to name hooks back when they were created.
I was able to fix this by grabbing my hooks from the management api and assigning each of them a
nameproperty using https://auth0.com/docs/api/management/v2#!/Hooks/patch_hooks_by_id.Not sure if this helps you, but figured i’d drop this here for anyone experiencing similar problems.
Ok, so the
idgets stripped out bythis.assets = stripIdentifiers(auth0, this.assets);in both directory and YAML exports:Directory export: https://github.com/auth0/auth0-deploy-cli/blob/f6b613bdac8ce03716d82b0597d76a0c76705526/src/context/directory/index.js#L71
YAML export: https://github.com/auth0/auth0-deploy-cli/blob/f6b613bdac8ce03716d82b0597d76a0c76705526/src/context/yaml/index.js#L112
Any reason why it would need to strip hooks ids?
It can be resolved by including
"AUTH0_EXPORT_IDENTIFIERS": truein your config, but if this is excluded (FYI the examples don’t include this option) it shouldn’t cause a bug with the export.