craftcms / craftcms/cms

Asset Volumes Not Deleting via Project.yaml

Open
#7,471 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
3.6k
Forks
705
Avg merge
1d 5h
Merged PRs (30d)
134

Description

Description

It appears that project config is not correctly apply changes to deleted volumes. Create a volume and then try to delete it via project config workflow. I can create new volumes, but can not delete.

Steps to reproduce
  1. Create new Asset volume in settings on local machine.
  2. See changes in project config yaml files and push to remote server and apply changes.
  3. Verify new volume is created on remote server
  4. Remove newly created Asset volume on local machine.
  5. Commit, push and apply changes to remote server.
  6. New volume is NOT deleted on remote server
  7. Check ./craft project-config/diff. -- 'No pending project config YAML changes'
Additional info
  • Craft version: 3.5.12.1
  • PHP version: 7.4.7
  • Database driver & version: MySQL 5.7.29
  • Plugins & versions:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the volume lifecycle using the project-config workflow described in the issue: create and apply an Asset volume, remove it locally, then apply the updated project.yaml files. Inspect project-config diff and the related project configuration handling; done means the remote volume is deleted and no pending YAML changes remain.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.