# Bootstrapping changes in workspaces

**URL:** <https://community.bloomreach.com/t/bootstrapping-changes-in-workspaces/1049>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [May 9, 2019, 9:07pm UTC](https://community.bloomreach.com/t/bootstrapping-changes-in-workspaces/1049 "2019-05-09T21:07:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![itGumby](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/itgumby/32/1326_2.png) [@itGumby](https://community.bloomreach.com/u/itGumby)\
**Post date:** [May 9, 2019, 9:07pm UTC](https://community.bloomreach.com/t/bootstrapping-changes-in-workspaces/1049/1 "2019-05-09T21:07:01Z")

</div>

I need to bootstrap a change to a hst:containeritemcomponent node because of code refactoring.

Because this is in a workspace, it is treated as content. So I thought I had to use a `hcm-actions.yaml` file per [Manage Content - Bloomreach Experience Manager (PaaS/Self-Hosted) - The Fast and Flexible Headless CMS](https://documentation.bloomreach.com/12/library/concepts/configuration-management/manage-content.html)

but I can’t seem to get the syntax for the file correct. My hippo-cms.log keeps complaining:

> 09.05.2019 15:01:28 ERROR localhost-startStop-1 [ConfigurationServiceImpl.start:127] Failed to start the ConfigurationService  
> javax.jcr.RepositoryException: org.onehippo.cm.model.parser.ParserException: Node must be a sequence in ‘reader’, line 1, column 14:  
> action-lists:  
> ^  
> at org.onehippo.cm.engine.ConfigurationServiceImpl.loadBootstrapModel(ConfigurationServiceImpl.java:516)

or

> 09.05.2019 15:05:25 ERROR localhost-startStop-1 [ConfigurationServiceImpl.start:127] Failed to start the ConfigurationService  
> javax.jcr.RepositoryException: org.onehippo.cm.model.parser.ParserException: Node must be a mapping in ‘reader’, line 2, column 9:  
> - 1.0:  
> ^  
> at org.onehippo.cm.engine.ConfigurationServiceImpl.loadBootstrapModel(ConfigurationServiceImpl.java:516) ~[hippo-repository-engine-5.0.2.jar:5.0.2]

Iterating on this is slow and painful. Is there any advice for bootstrapping workspace changes in Hippo 12.0.2?

---

<div class="post-metadata">

**Author:** ![itGumby](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/itgumby/32/1326_2.png) [@itGumby](https://community.bloomreach.com/u/itGumby)\
**Post date:** [May 9, 2019, 9:10pm UTC](https://community.bloomreach.com/t/bootstrapping-changes-in-workspaces/1049/2 "2019-05-09T21:10:03Z")

</div>

example hcm-actions.yaml:

> action-lists:
> 
> - 1.0:  
> /hst:hst/hst:configurations/myapp/hst:workspace/hst:containers/base/header: reload

---

<div class="post-metadata">

**Author:** ![itGumby](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/itgumby/32/1326_2.png) [@itGumby](https://community.bloomreach.com/u/itGumby)\
**Post date:** [May 10, 2019, 5:32pm UTC](https://community.bloomreach.com/t/bootstrapping-changes-in-workspaces/1049/3 "2019-05-10T17:32:29Z")

</div>

Bloomreach support provided an example hcm-actions.yaml file that parses and works for me:

```
action-lists:
  - 1.0:
    /hst:hst/hst:configurations/myhippoproject/hst:workspace/hst:containers/contentpage/main/content: reload

```

1. 0 spaces before “action-lists” line
2. 2 spaces before change set line ("- 1.0:")
3. **6 spaces** before node absolute path line

Thanks for your help!  
Brian

---

<div class="post-metadata">

**Author:** ![Ilakkia\_Baskar](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/ilakkia_baskar/32/2044_2.png) [@Ilakkia\_Baskar](https://community.bloomreach.com/u/Ilakkia_Baskar)\
**Post date:** [July 1, 2025, 3:35pm UTC](https://community.bloomreach.com/t/bootstrapping-changes-in-workspaces/1049/4 "2025-07-01T15:35:28Z")

</div>

Hello @itGumby ,

We are happy you are part of Bloomreach Developer’s Community.  
Thank you for reaching out to us.

We hope we have answered your queries and therefore marking this thread for Closure.  
We are delighted to acknowledge your ongoing contributions to our esteemed Bloomreach Community.

Best Regards,  
Bloomreach