drivebyer opened a new issue, #171:
URL: https://github.com/apache/rocketmq-operator/issues/171

   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
   - What did you do (The steps to reproduce)?
   
   run `make manifests`
   
   - What did you expect to see?
   No error and operator deployment manifests is generate in deploy&&charts 
directory.
   
   - What did you see instead?
   
   ```
   ➜  rocketmq-operator git:(master) make manifests
   Makefile:130: warning: overriding commands for target `docker-build'
   Makefile:122: warning: ignoring old commands for target `docker-build'
   
/Users/wuyang/workspace/github.com/drivebyer/rocketmq-operator/bin/controller-gen
 rbac:roleName=rocketmq-operator crd:generateEmbeddedObjectMeta=true webhook 
paths="./..." output:dir=deploy output:crd:artifacts:config=deploy/crds
   head -n 14 deploy/role_binding.yaml > deploy/role.yaml.bak
   cat deploy/role.yaml >> deploy/role.yaml.bak
   rm deploy/role.yaml && mv deploy/role.yaml.bak deploy/role.yaml && \
       cp deploy/role.yaml charts/rocketmq-operator/templates/role.yaml && \
       cp deploy/operator.yaml charts/rocketmq-operator/templates/operator.yaml 
&& \
       cp deploy/role_binding.yaml 
charts/rocketmq-operator/templates/role_binding.yaml && \
       cp deploy/service_account.yaml 
charts/rocketmq-operator/templates/service_account.yaml && \
       cp deploy/crds/* charts/rocketmq-operator/templates/crds/
   cp: charts/rocketmq-operator/templates/crds is not a directory
   make: *** [manifests] Error 1
   
   ```
   
   2. Please tell us about your environment:
   null
   
   3. Other information (e.g. detailed explanation, logs, related issues, 
suggestions how to fix, etc):
   Should fix the latest `cp` command of `manifests` target to:
   ```
   cp deploy/crds/* charts/rocketmq-operator/crds/
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to